Update usage-next-13.mdx: Clarify that the API route need to stay in the pages folder #848
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@tordans is attempting to deploy a commit to the Blitz Team on Vercel. A member of the Team first needs to authorize it. |
13 tasks
siddhsuresh
previously approved these changes
Oct 25, 2023
siddhsuresh
approved these changes
Oct 25, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current migration guide https://nextjs.org/docs/app/building-your-application/upgrading/app-router-migration#migrating-from-pages-to-app recommends
I tried moving the existing files to the app directory but that fails. Likely because the new app/api directory works differently. However, in general there are app/api routes documented in https://nextjs.org/docs/app/building-your-application/routing/route-handlers so maybe with updated files we can migrate…